Dorenbos/Hoogeveen/Leur
Dorenbos Hoogeveen Leur
Home Database Home Database Home History Notation Search Tips Links Contact
Notation
The notation used in this database was
designed to be as concise as possible for the purpose of building readily
readable, two-dimensional tree structures of extended families. You can think of it as a kind of genealogy
meta-index, combining and merging existing genealogical indexes in a way that
simultaneously captures the family relationships. Researching further genealogical information,
such as locations, lifestyles, in-laws, etc., is left to the users of this
database.
The formal rules of notation are:
1) Each node of the tree is a single text line
whose indentation level and location relative to its neighbors denote
its parent-child-sibling relationships.
2) The node format is: <principal> (<birthyear>--<deathyear>) & <spouse> (<birthyear>--<deathyear>) (<marriageyear>div<divorceyear>)
3) Any elements of this node may be missing.
4) The <principal> is the full name of the
Dorenbos/Hoogeveen/Leur family member, whether male or female. Occasionally family members of interest with
different surnames are included.
5) The <spouse> is the full birth name of
the spouse, if any. If the spouse is
also a principal elsewhere, the surname is a hyperlink to his or her birth
family in the appropriate database.
6) If the exact year of birth, death, or marriage
is unknown, an estimate may be present
using the conventional symbol <, >, or ~ (“before”, “after”, or “estimated
at”) based on what is known about the individual’s life.
7) Every principal has exactly one node or line—with
one exception: multiple marriages are expressed in multiple lines at the same
indentation level, much like siblings (below).
8) The parent-to-child relationship is expressed
by placing the first child immediately after its parent, indented one
level to the right, and followed by all further siblings at the same level. Siblings may be physically separated from
each other by (further indented) descendants of the prior sibling, but the
originally assigned indentation level is scrupulously retained for each sibling.
9) Siblings are usually ordered by birth
year, but this rule can be ignored for readability considerations, such as when
a younger sibling (or earlier marriage) has many descendants.
10) A surname in parentheses implies that
the name was assumed sometime after birth, usually when in transition from
patronymic to surname conventions. Typically, the earlier records for that
individual used patronymics alone, and later ones appended the new surname.
11) Occasionally parentheses are used for other
purposes as well, say, for nicknames or unusual spelling variants.
12) N.N. denotes an unknown or nonexistent given name, such as for an unnamed stillborn child or an
incomplete document entry.
13) A red node denotes
a speculated or “best-guess” relationship for that node, including all
its child nodes, to the previous line.
14) A red detail item
similarly denotes a “best guess” in the association of some detail.
15) Location data is aligned to the right of the page so as not
to distract from the family structure itself.
The format is (<birthplace/<spouse-birthplace>/<marriage-place/<any-other-place). The two middle items are omitted for
unmarried persons.
16) Square brackets are used for other comments,
especially witness information to help clarify relationships, and is inserted
to the left of the location data. Margins
are adjusted for space and readability considerations
17) Witness data: dget=doopgetuige; tget=trouwgetuige;
kget=kinds-doopgetuige.
18) Use of question marks (“?”) is limited to
flagging truly questionable or conflicting data.
© 2016 Annelies J. Schlitt The use of any material
derived from this website for commercial purposes without permission is
strictly forbidden.